Reallocation of Tape Drive Resources Associated With a Secure Data Erase Process

ABSTRACT

A method according to one embodiment includes determining whether to reallocate one or more of a plurality of tape drives that are presently allocated for a secure data erase process in response to an evaluation of a quantity of physical volumes to be secure data erased and a minimum queued threshold; and in response to said determination that one or more of said plurality of tape drives is to be reallocated, reallocating the one or more of said plurality of tape drives from the secure data erase process to another function.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.13/115,061, filed May 24, 2011, which is a continuation of U.S. patentapplication Ser. No. 11/737,739, filed Apr. 19, 2007, now U.S. Pat. No.8,006,050, from which priority is claimed and which are hereinincorporated by reference.

BACKGROUND

The disclosure relates generally to automated data storage systems andmore particularly, to a system and for selectively performing a securedata erase.

A virtual tape system is a tape management system such as a specialstorage device or group of devices and software which manages data suchthat the data appears to be stored entirely on tape cartridges whenportions of the data may actually be located in faster, hard diskstorage. Programming for a virtual tape system is sometimes referred toas virtual tape server (VTS), although these terms may be usedinterchangeably, unless otherwise specifically indicated. A virtual tapesystem may be used with hierarchical storage management (HSM) system inwhich data is moved as the data falls through various usage thresholdsto slower but less costly forms of storage media. A virtual tape systemmay also be used as part of a storage area network (SAN) whereless-frequently used or archived data can be managed by a single virtualtape server for a number of networked computers.

In prior art virtual tape storage systems, such as InternationalBusiness Machines (IBM) MAGSTAR Virtual Tape Server, at least onevirtual tape server (VTS) is coupled to a tape library comprisingnumerous tape drives and tape cartridges. The VTS is also coupled to adirect access storage device (DASD), comprised of numerousinterconnected hard disk drives.

The DASD functions as a tape volume cache (TVC) of the VTS subsystem.When using a VTS, the host application writes tape data to virtualdrives. The volumes written by the host system are physically stored inthe tape volume cache (e.g., a RAID disk buffer) and are called virtualvolumes. The storage management software within the VTS copies thevirtual volumes in the TVC to the physical cartridges owned by the VTSsubsystem. Once a virtual volume is copied or migrated from the TVC totape, the virtual volume is then called a logical volume. As virtualvolumes are copied from the TVC to a MAGSTAR cartridge (tape), they arecopied on the cartridge end to end, taking up only the space written bythe host application. This arrangement maximizes utilization of acartridge storage capacity.

The storage management software manages the location of the logicalvolumes on the physical cartridges, and the customer has no control overthe location of the data. When a logical volume is copied from aphysical cartridge to the TVC, the process is called recall and thevolume becomes a virtual volume again. The host cannot distinguishbetween physical and virtual volumes, or physical and virtual drives.Thus, the host treats the virtual volumes and virtual drives as actualcartridges and drives and all host interaction with tape data in a VTSsubsystem is through virtual volumes and virtual tape drives.

One issue of VTS systems is the management of data within the tapes. TheVTS system may have a number of duplicate, invalid, latent or unusedcopies of data. After a virtual tape volume is created and/or modified(one or more records are written to the volume) and closed, the virtualtape volume is copied onto the physical tape (logical) volume. The imageof the virtual volume copied to a physical volume when the virtualvolume was closed is a complete version of the virtual volume at thepoint in time the virtual volume was closed. If a virtual volume issubsequently opened and modified, when the virtual volume is closed,that image of the virtual volume is also copied onto physical tape,however the virtual volume does not overwrite the prior version of thevolume since the virtual volume may have a different size than theprevious version. So at any point in time, there may be several versionsof the same volume serial number that reside on one or more physicaltape volumes.

Moreover, physical volumes within a VTS are arranged in groups that arecalled “pools,” with each physical volume including one or more logicalvolumes. Each of the physical volumes managed by the VTS system isassigned to one of 32 pools, for example. It is understood that eachpool of physical volumes is assigned a name and may have one or moreparameters associated therewith. For example, typical parametersassociated with a pool include, but are not limited to: a media type(e.g. physical volumes having 10 Gbyte tape or 20 Gbyte tape); and arule(s) for managing volumes in a pool. One rule may involve the conceptof “reclamation” whereby the VTS monitors what percentage of dataassociated in a particular physical volume is still valid. That is, overtime, data space occupied by a logical volume needs to be reclaimed froma physical volume when the data is no longer used or needed by the host,i.e., has expired. Thus, if any volume(s) in the pool falls below areclaim percent threshold, then a reclamation process will be performedto take the valid logical volume(s) off the physical volume and put thevalid logical volume on another physical volume—potentially combiningmultiple partially full physical volumes and filling up the other.

If a virtual volume is removed from the physical volume and put on toanother physical volume, the data on the first physical volume isdeleted but has not been overwritten, and thus, the data may berecovered. Further, data associated with the most current version of avirtual volume may be expired or considered latent or unusable by thecustomer, but the virtual volume still will exist on the physical tapevolume and could be accessed.

Recently, enterprises have become more dependent on the ability tostore, organize, manage and distribute data. Accordingly, “informationlife-cycle management,” the process of managing business data fromconception until disposal in a manner that optimizes storage, access,and cost characteristics has become increasingly important. Inparticular, the significance of how data is “deleted” or disposed of hasincreased as confidential data has begun to play a more vital role inbusiness transactions and stricter regulations are imposed onmaintaining customer privacy.

To protect confidential or sensitive data (e.g., credit cardinformation, social security number) and to maintain customer privacy itis advantageous to perform a secure data erase on certain data so thatthe data is unrecoverable. A secure data erase is defined hereinrendering data permanently unreadable by any reasonable means. Prior artmethods of prioritizing data to be securely erased are performed by afirst in, first out priority basis, ensuring that the physical volumethat was first added to the queue for secure data erase is secure dataerased first. For example, in the prior art method the process todetermine which physical volume should be secure data erased next loopedthrough each pool of physical volumes beginning with pool 1 andcontinuing through all pools to the last pool (e.g. pool 32). Therefore,the list or queue of physical volumes to secure data erase is created byevaluating and listing all of the physical volumes within pool 1 to besecure data erased, then evaluating and listing all of the physicalvolumes within pool 2 to be secure data erased, and so on, continuing tothe last pool (e.g. pool 32), until all of the physical volumes in allthe pools that require secure data erase are evaluated and listed on thequeue. The secure data erase process is then initiated, and with a firstin, first out process the prior art process begins with a secure dataerase of the physical volumes in the order that they are listed in thequeue. Thus, the VTS performs a first secure data erase on thosephysical volumes that are in pool 1, then when the physical volumeswithin pool 1 are secure data erased, the VTS begins secure data eraseon the physical volumes within pool 2, and so on, continuing until theprocess reaches the last pool (e.g. pool 32).

The prior art process as described is sufficient provided the VTS canmanage all of the physical volumes to be secure data erased within thetime remaining to the erasure deadline or there is no backlog ofphysical volumes to be secure data erased. In reality the VTS system canbecome overloaded and, for example, while a physical volume within pool23 is being secure data erased a physical volume within pool 32 may passits secure data erase (SDE) deadline. Therefore, physical volumes thathave the shortest remaining time to the SDE deadline may be overlookedor postponed. This could put long-expired physical volumes which maycontain sensitive data (e.g., credit card information, social securitynumber) at risk for being accessed and retained.

Therefore, it would be advantageous to have a VTS system that givespriority for secure data erase to physical volumes closest to their SDEdeadline. Thus, what is needed is a method and a system that guaranteesthat old or expired versions of a virtual volume cannot be accessedafter a certain time interval (e.g. a grace period), through anyreasonable means.

BRIEF SUMMARY

A tape management system according to one embodiment includes aplurality of tape drives; and a processor coupled to said plurality oftape drives. The processor is configured to: determine whether toreallocate one or more of said plurality of tape drives that arepresently allocated for a secure data erase process in response to anevaluation of a quantity of physical volumes to be secure data erasedand a minimum queued threshold; and in response to said determinationthat one or more of said plurality of tape drives is to be reallocated,reallocate the one or more of said plurality of tape drives from thesecure data erase process to another function.

A method according to one embodiment includes determining whether toreallocate one or more of a plurality of tape drives that are presentlyallocated for a secure data erase process in response to an evaluationof a quantity of physical volumes to be secure data erased and a minimumqueued threshold; and in response to said determination that one or moreof said plurality of tape drives is to be reallocated, reallocating theone or more of said plurality of tape drives from the secure data eraseprocess to another function.

A computer program product for reallocating one or more of saidplurality of tape drives that are presently allocated for a secure dataerase process, according to one embodiment, includes a computer readablestorage medium having program code embodied therewith. The program codeis readable/executable by a processor to: determine, by the processor,whether to reallocate one or more of said plurality of tape drives thatare presently allocated for a secure data erase process in response toan evaluation of a quantity of physical volumes to be secure data erasedand a minimum queued threshold; and in response to said determinationthat one or more of said plurality of tape drives is to be reallocated,reallocate, by the processor, the one or more of said plurality of tapedrives from the secure data erase process to another function

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a detailed block diagram of a data storage networkincluding a data storage subsystem according to an embodiment of thepresent disclosure;

FIG. 2 illustrates a flow diagram of method to selectively perform asecure data erase in accordance with one embodiment of the presentdisclosure;

FIG. 3 illustrates a flow diagram of a method to evaluate the allocationof resources for secure data erase in accordance with another embodimentof the present disclosure; and

FIG. 4 illustrates a data processing system useable with one or moreembodiments of the present disclosure.

DETAILED DESCRIPTION

The following is intended to provide a detailed description of anexample of the invention and should not be taken to be limiting of theinvention itself. Rather, any number of variations may fall within thescope of the invention which is defined in the claims following thedescription.

The present disclosure allows for a method to ensure a timely securedata erase by giving priority for secure data erase to the physicalvolumes closest to their secure data erase deadline. Moreover, in oneembodiment, the present disclosure ensures timely secure data erase byallocating more tape drive devices to aid in the secure data eraseprocess when it is determined that the current allocation will not beable to meet the secure data erase demand. Finally, in a furtherembodiment, the present disclosure provides a process to return to aminimum allocation of tape drives when the minimum allocation of tapedrives will be able to meet the secure data erase demand.

While the tape management system is referred to herein as a Virtual TapeSystem (VTS), a VTS is only one example of a tape management system. Aswould be understood by one of ordinary skill in the art the presentdisclosure applies to any tape management system, such as a tape libraryand virtual tape software etc.

With reference now to FIG. 1, there is depicted a block diagram of anexemplary virtual storage system 100 that provides a suitableenvironment for the practice of the present disclosure. Virtual storagesystem 100 includes a virtual tape server 101, a tape library 112, and alibrary manager 130. A host system 102 is linked to the virtual tapeserver 101 via a network connection, e.g. TCP/IP, LAN, Ethernet, and theIBM Enterprise System Connection (ESCON) (not shown). In one embodiment,host system 102 is a computer, such as a personal computer, workstationor mainframe that is linked to the virtual tape server 101 via an ESCONchannel. Virtual tape server 101, in one embodiment, is a computerincluding a processor, such as a personal computer, workstation ormainframe and is associated with a Direct Access Storage Device (DASD)cache 106. The DASD cache 106 preferably includes one or more logicalvolumes. In one embodiment, DASD cache 106 includes a plurality of harddisks that are spaced into redundant array of inexpensive disk (RAID)arrays.

Tape library 112 includes a plurality of tape drives 110, generallydesignated tape drives 110A, 110B . . . 110N, such as InternationalBusiness Machine (IBM), TS1100 or JAGUAR 3592 tape drives or any othertape drive known in the art. Generally, a removable storage volume,e.g., a tape cartridge 116A, 116B, . . . 116N, is loaded into each ofthe tape drives. Tape storage drives 110 are serviced by an accessor(e.g., a robot) 114 which transfers selected tape cartridges 116A, 116B,. . . 116N between tape storage drives 110 and their correspondingpositions within a tape cartridge repository.

It will be noted that the variable identifier “N” is used in severalinstances in FIG. 1 to more simply designate the final element (e.g.,tape drives, 110A, 110B . . . 110N, and tape cartridges, 116A, 116B, . .. 116N) of a series of related or similar elements (e.g., tape drivesand tape cartridges). The repeated use of such variable identifiers isnot meant to imply a correlation between the sizes of such series ofelements, although such correlation may exist. The use of such variableidentifiers does not require that the series of elements has the samenumber of elements as another series delimited by the same variableidentifier. Rather, in each instance of use, the variable identified by“N” may hold the same or a different value than other instances of thesame variable identifier.

Tape library 112 typically includes storage management software utilizedto monitor the active space on the tape cartridges and schedulereclamations of tape cartridges when the system is less active. In oneembodiment, tape library 112 is a tape library system such as the IBMVirtualization Engine TS 7740 and IBM MAGSTAR 3494 Tape Library. Librarymanager 130 is utilized in virtual storage system 100 to install,maintain, configure, and operate tape library 112. Within automatedlibrary 112, accessor 114 may be controlled utilizing a library manager130 based upon inputs received from storage management server 108 and/oran automated storage management administrator 128.

DASD cache 106 that includes, in one embodiment, a tape volume cache,provides a cache for data stored in tape library 112. DASD cache 106maintains logical volumes as logical volume files that are concatenatedinto physical volume files in the tape cartridges loaded in the tapedrives located within tape library 112. When a logical volume file inDASD cache 106 moves to a tape drive in a tape library 112, the logicalvolume file is written to a physical volume file on a tape cartridge inthe actual tape drive. When a physical volume file is recalled for atape drive and moved to DASD cache 106, the physical volume file thenbecomes a logical volume file in the DASD cache 106. In this way, DASDcache 106 provides a window to host system 102 of all the physicalvolume files in tape library 112.

Virtual tape data storage system includes a plurality of virtual tapedaemons, generally designated as tape daemons 118A, 118B, . . . 118N,that represent and emulate virtual tape devices to host system 102. Hostsystem's 102 operating system, in turn, manages the presentation of thevirtual tape devices to the systems users (not shown). Host system 102views the virtual tape devices as actual drives and when host system 102attempts to access a logical volume in a selected virtual tape device,the respective virtual tape daemon associated with the virtual tapedevice requested by the host system 102 will handle the host accessrequest.

Host-to-DASD cache data transfer in the illustrated virtual tape datastorage subsystem may be controlled by VTS code via a process such as ahierarchical storage manager (HSM) client 122. For example, a HSM client122 within virtual storage system 100 intercepts and processes theaccess request from the virtual tape daemons 118A, 118B, . . . 118N. HSMclient 122 then carries out host system 102 request to access thelogical volume file on DASD cache 106. In one embodiment, host-to-DASDcache data transfer is directly controlled by a file system manager(FSM) 120A, 120B, . . . 120N which handles DASD read and write commands.

Similarly, an interface between the DASD cache 106 and the tape storagedrive 110 may be controlled by storage management server 108. Forexample, if HSM client 122 attempts to mount a logical volume file thatis not located in DASD cache 106, HSM client 122 will communicate theaccess request to the storage manager server 108. If the tape in theaccess request is already mounted in a tape drive in tape library 112,storage manager server 108 will access the physical volume for therequested logical volume file from the mounted tape. However, if therequested file on a tape is not presently mounted in a tape drive, thestorage manage server 108 will initiate a request to library manger 130to mount the tape containing the physical volume corresponding to therequested logical volume file.

Examples of a storage management processing module which could be usedas storage management server 108 and HSM client 122 are the TivoliStorage Manager (TSM) application and IBM ADSTAR Distributed StorageManager (ASDM) product, both of which are provided by InternationalBusiness Machines Corporation of Armonk, N.Y.. In data storage network100, storage management server 108 includes a command interface 124 anda console output 126.

In a one embodiment, storage manager server 108 migrates entire logicalvolume files from DASD cache 106 to tape library 112. When the availablespace in DASD cache 106 reaches a predetermined level or after apredetermined time period, and automated storage managementadministrator 128 will direct storage manager server 108 to migratelogical volume files from DASD cache 106 to tape library 112 forarchival therein. Typically, automated storage management administrator128 stores information associated with the physical volumes in anassociated volume status table (not shown). According to one embodiment,automated storage management administrator 128 provides functionalityneeded to achieve the secure data erase process of the presentdisclosure, and additionally performs many VTS specific administrativefunctions utilizing storage management server 108. For example,automated storage management administrator 128 may include a secure dataerase processing module.

The requirement that the old version(s) of the VTS volume must behandled to guarantee that they cannot be recovered is met by overwritinga physical volume that contains invalidated virtual volume data within acertain time interval (i.e. grace period) specified by the customer.Thus, there is introduced a function, implemented by the VTS, andparticularly, the automated storage management administrator 128component of the VTS, for enabling data associated with a virtual orlogical volume to be invalidated. A physical volume and its associateddata may be secure data erased (i.e., rendered permanently unreadable byany reasonable means) by overwriting all data of the physical volume oneor more times utilizing a predetermined file or data pattern (e.g.,logical ones, zeroes, some combination thereof). Techniques for thesecure data erase process may be user or host-selectable (e.g., basedupon a desired level of security) or automatically determined. Theoverwriting may be performed by one of the tape drives 110A, 110B . . .110N.

An expiration time is provided at which the data on a physical volume isinvalid, latent or unused. The data may become invalid, latent, orunused by reclamation, migration or modification, for example, asdescribed above. The expiration time may be a date, or a date and a timeof day, at which the data is not longer valid or useful, and hereinafterwill be referred to as the expiration date. A secure data erasure (SDE)deadline is set for each physical volume of a plurality of physicalvolumes after a certain time interval (i.e. grace period) after theexpiration date and may be set by the customer (e.g. customer securedata erasure deadline). The SDE deadline is the date at which the securedata erase must be performed to avoid retention of unwanted data. It isadvantageous to perform a secure data erase within a certain timeinterval (i.e. a grace period) from the expiration time to ensure thatconfidential data and customer information will be kept for a requiredperiod of time, but cannot be recovered by any reasonable means afterthe required period of time. For example, documents such as bank recordsand credit card information may be required to be held for a certaintime interval (i.e. grace period) by law. However, after this requiredtime interval (i.e. grace period) has passed it is advantageous for thecompany to secure data erase the information, such that the informationis no longer recoverable. Thus, for a given pool, it is desired toensure that after a certain time interval (i.e. grace period), expireddata on a physical volume is no longer accessible through any normalmeans, such as by overwriting the expired data.

FIG. 2 discloses a process that periodically determines which of thephysical volumes managed by the VTS should be the next physical volumeto be securely data erased. For purposes of discussion, it is assumedthat this process is machine executed instructions executed by the VTS(on a daily basis, e.g., every 24 hours, etc. however, the process maybe performed every 12 hours, or any granularity as appropriate). Asshown in FIG. 2, the process begins at step 202 where the VTS obtains aphysical volume (or the next physical volume) to evaluate therequirements for secure data erasure.

While it is described that the VTS performs various functions during theprocess disclosed in FIG. 2 and FIG. 3 it is understood by one ofordinary skill in the art that it may be the application running on theprocessor of the VTS such as the direct storage manager server 108 (e.g.TSM server), HSM client 122 (e.g. TSM HSM client), or the automatedstorage management administrator 128 (e.g. TSM automated administrator)that may perform these functions.

In step 204, the VTS determines if the current date is later than anexpiration date of the selected physical volume. The expiration date ofa physical volume is defined as the time and/or date when the datacontained within the physical volume is considered invalid, latent, orno longer useful.

If a determination is made that the current date is not later than theexpiration date then the process proceeds to process block 214. Inprocess block 214 the VTS (e.g. an application running on the processorsuch as the direct storage manager server 108, HSM client 122, orautomated storage management administrator 128) determines if thephysical volume currently being evaluated is the last physical volume.In the case where the physical volume currently being evaluated is thelast physical volume then the process continues on to step 216. If it isdetermined that the physical volume currently being evaluated is not thelast physical volume then the process proceeds to step 202, wherein theVTS obtains the next physical volume to evaluate.

However, if it is determined that the current date is later than theexpiration date the process proceeds to step 206, wherein the VTSdetermines whether or not the physical volume is available for securedata erase. The VTS may determine whether or not the physical volume isavailable for secure data erase based on a number of factors. Forexample, a physical volume will not be available for secure data eraseif the physical volume is currently being filled with additional data orif the physical volume or portions of the physical volume are being readetc.

If it is determined that the physical volume is not available for securedata erase the process continues to process block 214. In process block214 the VTS determines if the physical volume currently being evaluatedis the last physical volume. In the case where the physical volumecurrently being evaluated is the last physical volume then the processcontinues on to step 216. If it is determined that the physical volumecurrently being evaluated is not the last physical volume then theprocess proceeds to step 202, wherein the VTS obtains the next physicalvolume to evaluate.

If it is determined in step 206 that the physical volume is availablefor secure data erase the process continues to step 208 in which the VTScalculates the remaining time. The remaining time can be defined as thetime remaining between the current date (e.g. today's date and/or time)to the secure data erasure (SDE) deadline. The remaining time iscalculated by the difference between the SDE deadline and the currentdate. For example, if the SDE deadline as Jul. 26, 2006 and the currentdate is Jul. 11, 2006, the calculated remaining time would be 15 days.One of ordinary skill in the art would understand that the remainingtime may be expressed in days, hours, minutes or seconds, asappropriate.

In step 210, the VTS compares the remaining time to a time threshold.The time threshold is a time period that may be defined by the customer.The time threshold, in one embodiment, may be a time period that thecustomer determines is close enough to the SDE deadline that secure dataerasure of the physical volume is warranted. For example, one customermay define a time threshold of 10 days from the SDE deadline, whileanother customer may define a time threshold of 5 days from the SDEdeadline.

If the VTS determines that the remaining time is greater than the timethreshold then the process continues to step 214. In step 214 the VTSdetermines if the physical volume currently being evaluated is the lastphysical volume. In the case where the physical volume currently beingevaluated is the last physical volume then the process continues on tostep 216. If it is determined that the physical volume currently beingevaluated is not the last physical volume then the process proceeds tostep 202, wherein the VTS obtains the next physical volume to evaluate.

In one embodiment, in addition to the steps described above, if it isdetermined that the remaining time is less than a time threshold theprocess continues to step 212 wherein the VTS increments a count. Theincrementing of a count allows for a record of the quantity of physicalvolumes to be secure data erased (physical volumes queued for securedata erasure) that are currently expired, are available for secure dataerasure, and that have a remaining time that is less than the customerdefined time threshold. The record of the quantity of physical volumesto be secure data erased (e.g. a physical volume erase count) may beadvantageous for determining allocation of additional resources for thesecure data erase process, as discussed below with respect to anotherembodiment of the present disclosure.

Following step 212, the process continues to step 214. In process block214 the VTS determines if the physical volume currently being evaluatedis the last physical volume. In the case where the physical volume beingevaluated is the last physical volume then the process continues on tostep 216. If it is determined that the physical volume currently beingevaluated is not the last physical volume then the process proceeds tostep 202, wherein the VTS obtains the next physical volume to evaluate.

The process continues as described until all of the physical volumeswithin all the pools have been evaluated. Once all the physical volumesin all of the pools have been evaluated the process continues to step216 in which the physical volumes are sorted by remaining time.

In step 218, in response to the sorting of the physical volumes based onthe remaining time, the VTS (or a processor (not shown) within the VTS)sends a command to the drive to secure data erase the physical volumewith the least or shortest amount of remaining time. As used herein theshortest amount of remaining time is the calculated time remaining withthe smallest difference between the current date (e.g. today's dateand/or time) to the secure data erasure (SDE) deadline. The driveperforms the secure data erase by overwriting all data of the physicalvolume one or more times utilizing a predetermined file or data pattern(e.g., logical ones, zeroes, some combination thereof). Once the securedata erase is performed the drive sends a response to the VTS (e.g. tothe HSM client via the storage management server) indicating the securedata erase has been performed. If however, the drive does not respondthat the secure data erase has been performed then the physical volumewill remain in the queue of physical volumes to be secure data erased.In the case where there are more physical volumes that are currentlyexpired, are available for secure data erasure, and that have aremaining time that is less than the customer defined time threshold,the VTS will continue to secure data erase the next physical volume withthe least or shortest remaining time until all physical volumes that arecurrently expired, are available for secure data erasure, and that havea remaining time that is less than the customer defined time thresholdare secure data erased.

As discussed above, the automated storage management administrator 128stores information associated with the physical volumes in an associatedvolume status table (not shown). The volume status table (not shown)lists each of the physical volumes in the system and includes one ormore parameters associated with the physical volume. In one embodiment,the volume status table may contain one or more of the following: theexpiration date for each physical volume; the time interval (i.e. graceperiod) for each physical volume; the secure data erase (SDE) deadlinefor each physical volume; remaining time (calculated in step 208); andthe number or quantity of secure data erasures queued (as counted anddetermined in step 212). The volume status table may be updatedperiodically, e.g., each time the process is initiated, to maintaincurrent parameters associated with each physical volume. The volumestatus table may also have additional information which would be helpfulin the secure data erase process as understood by one of ordinary skillin the art.

Each of the blocks of the flow diagram of FIG. 2, and those depicted insubsequent figures, may be executed by a module (e.g., a softwaremodule) or a portion of a module or a computer system. The methodsdescribed herein, the operations thereof and modules for performing suchmethods may therefore be executed on a computer system configured toexecute the operations of the method and/or may be executed fromcomputer-readable media. The method may be embodied in amachine-readable and/or computer-readable medium for configuring acomputer system to execute the method. The software modules may bestored within and/or transmitted to a computer system memory toconfigure the computer system to perform the functions of the module.Alternatively, such actions may be embodied in the structure ofcircuitry that implements such functionality, such as the micro-code ofa complex instruction set computer (CISC) or reduced instruction setcomputer (RISC), firmware programmed into programmable orerasable/programmable devices, the configuration of a field-programmablegate array (FPGA), the design of a gate array or full-customapplication-specific integrated circuit (ASIC), or the like.

Those skilled in the art will also recognize that the boundaries betweenmodules and operations depicted herein are merely illustrative andalternative embodiments may merge such modules or operations, or imposean alternative decomposition of functionality thereon. For example, theactions discussed herein may be decomposed into sub-operations to beexecuted as multiple computer processes. Moreover, alternativeembodiments may combine multiple instances of a particular operation orsub-operation. Furthermore, those skilled in the art will recognize thatthe operations described in exemplary embodiment are for illustrationonly. Operations may be combined or the functionality of the operationsmay be distributed in additional operations in accordance with thedisclosure. As will also be apparent to those of skill in the art,methods for determining delay and jitter described herein may employother techniques (similar in effect to those described herein) to makesuch determinations, and such alternative techniques are intended to becomprehended by the methods and apparati discussed herein.

FIG. 3 illustrates a process flow diagram in which additional resources(e.g. tape drive(s)) may be allocated to perform the secure data erase,or alternatively, one or more existing tape drives (tape drivesallocated to the secure data erase process) may be reallocated such thatone or more previous additional allocated resources (e.g. tape drive(s))may be removed, one or more additional resources (e.g. tape drive(s))may be added, or the resources may be set back to the minimumrequirement. The addition of tape drive resources is determined based onwhether allocating the additional tape drive(s) would improve the securedata erase performance. An improvement may be the ability of the tapemanagement system (e.g. VTS) to perform the secure data erasure beforethe secure data erasure deadline as described further below. The removalof tape drive resources is determined based on whether or not the securedata erase process would be able to operate and meet the secure dataerase deadline(s) with fewer tape drives or with the number of tapedrives allocated for minimum operating requirements.

As discussed above with respect to step 212 an incremental count of thenumber or quantity of physical volumes that are currently expired, areavailable for secure data erasure, and have a remaining time that isless than the customer defined time threshold may be kept. In otherembodiments a count of physical volumes to be secure data erased may beobtained by other methods. The count of physical volumes that arecurrently expired, are available for secure data erasure, and have aremaining time less than the customer defined time threshold defines thenumber or quantity of secure data erase operations that are queued.

FIG. 3 illustrates flow diagram of a method to evaluate the allocationof resources (e.g. tape drive(s)) for secure data erase in accordancewith an embodiment of the present disclosure. For purposes ofdiscussion, it is assumed that this process is code executed by the VTSupon a request for a secure data erase, upon a customer request, or on aperiodic basis (e.g., every 24 hours, every 12 hours, or any granularityas appropriate). The process flow begins at step 301 and flows to step302. As illustrated in step 302, the VTS compares the number or quantityof secure data erase operations that are queued against a maximum queuedthreshold. The maximum queued threshold may be defined by the customer.For example, the customer may determine the maximum queued threshold asthe quantity of physical volumes that the VTS system, with the currentresources could successfully secure data erase without exceeding asecure data erase deadline. For example the customer may define themaximum queued threshold to be 15 physical volumes.

If the quantity of secure data erase operations that are queued (forexample, 16) are greater than the maximum queued threshold then theprocess continues to step 306. In step 306 the average time to thecustomer secure data erase (SDE) deadline is calculated and compared toa minimum expiration threshold. The average time to SDE deadline isdetermined by summing the remaining time for each physical volume to theSDE deadline in the secure data erase queue and dividing the sum by thequantity of physical volumes in the secure data erase queue. The minimumexpiration threshold may be defined by the customer. For example, thecustomer may determine and define the minimum expiration threshold byconsidering the minimum amount of time (e.g. number of days or hours)that the customer can reasonably expect the current allocation of securedata erase drives to be able to secure data erase the quantity ofphysical volumes queued before they reach the SDE deadline. If theaverage time to SDE deadline is greater than the minimum expirationthreshold then the process ends at step 312 without allocating orremoving any secure data erase resources. For example, if the averagetime to SDE deadline is 15 days, and the minimum expiration thresholdhas been set by the customer to 3 days then it would be expected thatthe current secure data erase resources (e.g. tape drives) aresufficient to secure data erase the queued physical volumes before theSDE deadline.

If the average time to customer SDE deadline is less than the minimumexpiration threshold then the process continues to step 310 in which theVTS allocates more tape resources (e.g. tape drives) to complete thequeued secure data erasure operations. For example, if the average timeto SDE deadline is 1 day, and the minimum expiration threshold has beenset by the customer to 3 days then it would be expected that the currentsecure data erase resources (e.g. tape drives) will not be able to meetthe demand to secure data erase all the physical volumes within thesecure data erase queue. In this example, the process would continue tostep 310 and an additional tape drive would be allocated for the securedata erase process. After step 310 the process continues to step 312where the process ends.

In one embodiment the VTS may allocate an additional tape drive(s) byrecruiting one of the tape drives 110A, 110B . . . 110N to perform theoverwriting process of secure data erase. The recruited tape drive (e.g.one of 110A, 110B . . . 110N) may have been previously used within theVTS to perform read and or write processes. Since the tape drive (e.g.one of 110A, 110B . . . 110N) is no longer able to perform thosefunctions, the VTS system is now functioning with one less drive toperform read and write operations. Therefore, it is desirable toallocate only the additional resource (e.g. tape drive) when theadditional resource is needed and to return the resource (e.g. tapedrive) to its original function when the additional resource is nolonger needed.

In another embodiment the VTS may allocate an additional tape drive tothe secure data erase process by requesting an additional tape drive tobe added to the tape library 112. The request may be communicatedthrough an interface such a display or graphical user interface (GUI).In another embodiment one or more additional resources (e.g. tapedrive(s)) may be allocated to perform the secure data erase.

Returning to step 302, if it is determined that the quantity of securedata erase operations that are queued are less than the maximum queuedthreshold the process continues to step 304. In step 304 the quantity ofsecure data erase operations is compared to a minimum queued threshold.The minimum queued threshold may be defined by the customer. Thecustomer may determine and define the minimum queued threshold as thequantity of secure data erases that will likely be secure data erasedbefore they have a chance of reaching the SDE deadline with the minimumoperating requirements. If the quantity of secure data erase operationsis less than the minimum queued threshold then the allocation of tapedrives for the secure data erase process are set to the minimumoperating requirements. In another embodiment, one or more existing tapedrives (tape drives allocated to the secure data erase process) may bereallocated such that one or more previous additional allocatedresources (e.g. tape drive(s)) may be removed. After step 308 theprocess ends at step 312.

If it is determined by the VTS that the quantity of secure data eraseoperations is greater than the minimum queued threshold then the currentallocation of tape drive resources is maintained and the process ends atstep 312.

In a further embodiment the allocation of tape drives for the securedata erase process may be performed at once, rather than in a piecemealfashion as described above. The VTS system may determine the optimumnumber of tape drives for a secure data erase process by performingsteps 302, 304, 306, 308, and 310 as previously described. Once theoptimum number of drives is determined the VTS allocates the optimumnumber of drives for the secure data erase process as described above.The optimum number of tape drives for a secure data erase process is theminimum number of tape drives that are required to perform the securedata erasure before the secure data erasure deadline. The optimum numbermay be reevaluated at periodic intervals (e.g. on a daily basis, every12 hours, or any granularity as appropriate).

FIG. 2 and FIG. 3 illustrate a flow diagram of the secure data eraseprocess according to an embodiment of the present disclosure. Althoughthe flow diagrams depicted in FIG. 2 and FIG. 3 indicate a particularorder of operations and a specific granularity of process operations inalternative embodiments the illustrated order may be varied (e.g.,process operations may be performed in another order or performedsubstantially in parallel) and one or more of the process operations maybe coalesced or fragmented). Similarly, additional process operationsmay be added where necessary in alternative embodiments of the presentdisclosure.

As discussed above, the automated storage management administrator 128stores information associated with the physical volumes in an associatedvolume status table (not shown). The volume status table lists each ofthe physical volumes in the system and includes one or more parametersassociated with the physical volume. In one embodiment, the volumestatus table may contain one or more of the following: the number ofsecure data erasures queued (as determined in step 212); and/or theaverage time to SDE deadline. This volume status table may be combinedwith the volume status table described above with respect to FIG. 2, orthe volume status table may be created as a separate table. The volumestatus table may be updated periodically, e.g., each time the process ofFIG. 2 and/or FIG. 3 is initiated, to maintain current parametersassociated with each physical volume. The volume status table may alsohave additional information which would be helpful in the secure dataerase process as understood by one of ordinary skill in the art.

FIG. 4 illustrates a data processing system useable with one or moreembodiments of the present disclosure. While a particular number andarrangement of elements have been illustrated with respect to dataprocessing system 400 of FIG. 4, it should be appreciated thatembodiments of the present disclosure are not limited to data processingsystems having any particular number, type, or arrangement of componentsand so many encompass a wide variety of data processing system types,architectures, and form factors (e.g., network elements or nodes,personal computers, workstations, servers, or the like). Data processingsystem 400 of the illustrated embodiment includes a processor 402coupled to a memory 404 utilizing a bus 406. Memory 404 may comprise anyof a number of system memory-type storage elements such as random accessmemory (RAM), read-only memory (ROM), flash memory, and cache.

Data processing system 400 of the illustrated embodiment furthercomprises an input/output (I/O) interface 408 coupled to bus 406 tocommunicatively couple one or more I/O devices (not shown) to dataprocessing system 400. Exemplary I/O devices may include traditional I/Odevices such as keyboards, displays, printers, cursor control devices(e.g., trackballs, mice, tablets, etc.), speakers, and microphones;storage devices such as fixed or “hard” magnetic media storage devices,optical storage devices (e.g., CD or DVD ROMs), solid state storagedevices (e.g., USB, Secure Digital SD™, CompactFlash™, MMC, or thelike), removable magnetic medium storage devices such as floppy disksand tape, or other storage devices or mediums; and wired or wirelesscommunication devices or media (e.g., communication networks accessedvia modem or direct network interface).

Embodiments of the present disclosure may include software, informationprocessing hardware, and various processing operations further describedherein. The features and process operations of the present disclosuremay be embodied in executable instructions embodied within amachine-readable medium such as memory 404, a storage device, acommunication device or medium, or the like. A machine-readable mediummay include any mechanism that provides (i.e., stores and/or transmits)data in a form readable by a machine (e.g., data processing system 400).For example, a machine-readable medium includes but is not limited to:random access memory (RAM); read only memory (ROM); magnetic storagemedia; optical storage media; flash memory devices; electrical, optical,and/or acoustical propagated signals (e.g., carrier waves, infraredsignals, digital signals, etc.); or the like. The described executableinstructions can be used to cause a general or special purpose processorsuch as processor 402, programmed with the instructions, to performoperations, methods or processes of the present disclosure.Alternatively, the features or operations of the present disclosure maybe performed by specific hardware components that contain hard-wiredlogic for performing the operations, or by any combination of programmeddata processing components and custom hardware components.

The present disclosure has been described in the context of fullyfunctional data processing system; however, those skilled in the artwill appreciate that the present disclosure is capable of beingdistributed as a program product in a variety of forms and appliesequally regardless of the particular type of signal bearing media usedto carry out the distribution. Examples of such signal bearing mediainclude recordable media such as floppy disks and CD-ROM, transmissiontype media such as digital and analog communications links, as well asmedia storage and distribution systems developed in the future.Embodiments of the present disclosure may similarly be implementedutilizing software modules used to perform certain operations or tasks.The described software modules may include script, batch, or otherexecutable files and may be stored on a machine-readable orcomputer-readable medium. Thus, the modules may be stored within acomputer system memory to configure a data processing or computer systemto perform one or more functions of a software module. Other new andvarious types of machine or computer-readable storage media may be usedto store the modules discussed herein.

While particular embodiments of the present invention have been shownand described, it will be obvious to those skilled in the art that,based upon the teachings herein changes and modifications may be madewithout departing from this invention and its broader aspects and,therefore, the appended claims are to encompass within their scope allsuch changes and modifications as are within the true spirit and scopeof this invention. Furthermore, it is to be understood that theinvention is solely defined by the appended claims.

1. A tape management system comprising: a plurality of tape drives; anda processor coupled to said plurality of tape drives, wherein saidprocessor is configured to: determine whether to reallocate one or moreof said plurality of tape drives that are presently allocated for asecure data erase process in response to an evaluation of a quantity ofphysical volumes to be secure data erased and a minimum queuedthreshold; and in response to said determination that one or more ofsaid plurality of tape drives is to be reallocated, reallocate the oneor more of said plurality of tape drives from the secure data eraseprocess to another function.
 2. The tape management system of claim 1,wherein the reallocation of the one or more of said plurality of tapedrives results in a number of said tape drives allocated to the securedata erase process being at a predetermined minimum requirement.
 3. Thetape management system of claim 1, wherein the determining whether toreallocate one or more of said plurality of tape drives is based onwhether the secure data erase process is able to meet one or more securedata erase deadlines with fewer tape drives than a number of tape drivespresently allocated to the secure data erase process.
 4. The tapemanagement system of claim 1, wherein the determining whether toreallocate one or more of said plurality of tape drives is based onwhether the secure data erase process is able to meet one or more securedata erase deadlines with a predefined minimum number of tape drivesallocated to the secure data erase process.
 5. The tape managementsystem of claim 1, wherein said processor is further configured to:compare said quantity of physical volumes to be secure data erased to amaximum queued threshold; and determine whether an allocation of anadditional tape drive would improve secure data erase performance whensaid quantity of physical volumes to be secure data erased is greaterthan said maximum queued threshold; and in response to saiddetermination that said allocation of an additional tape drive wouldimprove said secure data erase performance, allocate an additional tapedrive for said secure data erase process.
 6. The tape management systemof claim 1, wherein said quantity of physical volumes to be secure dataerased is determined by a physical volume erase count, wherein saidphysical volume erase count is determined by incrementing a count foreach physical volume that has a remaining time less than a timethreshold.
 7. The tape management system of claim 6, wherein saidprocessor is configured to determine said remaining time by calculatinga difference between said erasure deadline of said physical volume and acurrent date of said physical volume.
 8. The tape management system ofclaim 1, said processor is further configured to: in response to saidtape management system receiving a request to perform a secure dataerase process, determine whether an allocation of an additional tapedrive would improve secure data erase performance, said determinationcomprising an evaluation of a quantity of physical volumes to be securedata erased, a maximum queued threshold, an average time to an erasuredeadline, and a minimum expiration threshold; and in response to saiddetermination that said allocation of an additional tape drive wouldimprove said secure data erase performance, allocate an additional tapedrive for said secure data erase process.
 9. A method comprising:determining whether to reallocate one or more of a plurality of tapedrives that are presently allocated for a secure data erase process inresponse to an evaluation of a quantity of physical volumes to be securedata erased and a minimum queued threshold; and in response to saiddetermination that one or more of said plurality of tape drives is to bereallocated, reallocating the one or more of said plurality of tapedrives from the secure data erase process to another function.
 10. Themethod of claim 9, wherein the reallocation of the one or more of saidplurality of tape drives results in a number of said tape drivesallocated to the secure data erase process being at a predeterminedminimum requirement.
 11. The method of claim 9, wherein the determiningwhether to reallocate one or more of said plurality of tape drives isbased on whether the secure data erase process is able to meet one ormore secure data erase deadlines with fewer tape drives than a number oftape drives presently allocated to the secure data erase process. 12.The method of claim 9, wherein the determining whether to reallocate oneor more of said plurality of tape drives is based on whether the securedata erase process is able to meet one or more secure data erasedeadlines with a predefined minimum number of tape drives allocated tothe secure data erase process.
 13. The method of claim 9, furthercomprising: comparing said quantity of physical volumes to be securedata erased to a maximum queued threshold; and determining whether anallocation of an additional tape drive would improve secure data eraseperformance when said quantity of physical volumes to be secure dataerased is greater than said maximum queued threshold; and in response tosaid determination that said allocation of an additional tape drivewould improve said secure data erase performance, allocating anadditional tape drive for said secure data erase process.
 14. The methodof claim 9, wherein said quantity of physical volumes to be secure dataerased is determined by a physical volume erase count, wherein saidphysical volume erase count is determined by incrementing a count foreach physical volume that has a remaining time less than a timethreshold.
 15. The method of claim 14, further comprising determiningsaid remaining time by calculating a difference between said erasuredeadline of said physical volume and a current date of said physicalvolume.
 16. The method of claim 9, further comprising: in response tosaid method receiving a request to perform a secure data erase process,determine whether an allocation of an additional tape drive wouldimprove secure data erase performance, said determination comprising anevaluation of a quantity of physical volumes to be secure data erased, amaximum queued threshold, an average time to an erasure deadline, and aminimum expiration threshold; and in response to said determination thatsaid allocation of an additional tape drive would improve said securedata erase performance, allocate an additional tape drive for saidsecure data erase process.
 17. A computer program product forreallocating one or more of said plurality of tape drives that arepresently allocated for a secure data erase process, the computerprogram product comprising a computer readable storage medium havingprogram code embodied therewith, the program code readable/executable bya processor to: determine, by the processor, whether to reallocate oneor more of said plurality of tape drives that are presently allocatedfor a secure data erase process in response to an evaluation of aquantity of physical volumes to be secure data erased and a minimumqueued threshold; and in response to said determination that one or moreof said plurality of tape drives is to be reallocated, reallocate, bythe processor, the one or more of said plurality of tape drives from thesecure data erase process to another function
 18. The computer programproduct of claim 17, wherein the reallocation of the one or more of saidplurality of tape drives results in a number of said tape drivesallocated to the secure data erase process being at a predeterminedminimum requirement.
 19. The computer program product of claim 17,wherein the determining whether to reallocate one or more of saidplurality of tape drives is based on whether the secure data eraseprocess is able to meet one or more secure data erase deadlines withfewer tape drives than a number of tape drives presently allocated tothe secure data erase process.
 20. The computer program product of claim17, wherein the determining whether to reallocate one or more of saidplurality of tape drives is based on whether the secure data eraseprocess is able to meet one or more secure data erase deadlines with apredefined minimum number of tape drives allocated to the secure dataerase process.